feat: Added dry run feature for default tx executor and logs file #96
Conversation
|
This feature may be named as |
I know, I added that functionality to do some tests, what you say is a good idea, add the possibility to simulate the transaction and if it is completed correctly then launch the real transaction, it would be nice to have 3 modes, no simulate, simulate and simulate and release tx, I'll keep in mind for next updates |
nikola43
changed the title
I agree with this, IMO this should be a running mode. Also, preflight is enabled by default, not sure if we need the 3rd mode. The simulation will happen when using warp or default executor right now. |
| try { | ||
| open({ | ||
| library: 'tpu_client', // key | ||
| path: "/Users/kasiopea/dev/rust/tpu-sol-test/target/aarch64-apple-darwin/release/libtpu_client.dylib" // path |
There was a problem hiding this comment.
I've been researching how to call the TPU as people say transactions are faster, I've tried using
https://github.com/lmvdz/tpu-client but it doesn't work because solana migrated to quic, so the only way I've had to use it from TS is creating a mini library in rust and doing binding to ts using ffi-rs, this is the code
https://github.com/nikola43/tpu_client
So i serialize tx and send it to tpu_client for release it
I forgot add compiled library to project and leave my local path, my idea is build for mac, windows and linux for bot be compatible with any OS.
https://solana.stackexchange.com/questions/9502/optimal-transaction-execution-speed
Added feature to simulate transactions using the default tx executor, has been added for testing / benchmarking purposes.
Also added functions to write to a log file the transactions performed by the bot for further analysis.